Dynamic page previewer for a web application builder

ABSTRACT

Disclosed are examples of systems, apparatus, methods and computer program products for providing a dynamic page previewer for a web application builder. A database system maintains a multi-tenant non-relational database associated with a number of users, web applications, and web application components. The system displays a user interface for a dynamic page previewer, consisting of a preview page for a web application containing a number of web application components and one or more component toggle buttons corresponding to the components. The system then processes a user request to select a component toggle button. One or more component visibility rules associated with the component are determined, as well as a visibility state for the component. The visibility state is modified in relation to the component visibility rules, and the system presents the preview page of the web application in the user interface with the web application component being visible or not visible based on the modified visibility state.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the United States Patent and Trademark Office patent file or records but otherwise reserves all copyright rights whatsoever.

TECHNICAL FIELD

This patent document generally relates to non-relational database systems, and more specifically to providing a dynamic page previewer for a web application builder.

BACKGROUND

“Cloud computing” services provide shared resources, applications, and information to computers and other devices upon request. In cloud computing environments, services can be provided by one or more servers accessible over the Internet rather than installing software locally on in-house computer systems. As such, users having a variety of roles can interact with cloud computing services.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve only to provide examples of possible structures and operations for the disclosed inventive systems, apparatus, methods and computer program products for providing a dynamic page previewer for a web application builder. These drawings in no way limit any changes in form and detail that may be made by one skilled in the art without departing from the spirit and scope of the disclosed implementations.

FIG. 1 shows a system diagram of an example of a system 100 for providing a dynamic page previewer for a web application builder, in accordance with some implementations.

FIG. 2 shows a flowchart of an example of a method 200 for providing a dynamic page previewer for a web application builder, performed in accordance with some implementations

FIG. 3 shows an example of a web application builder, in accordance with some implementations.

FIG. 4 shows an example of a dynamic page previewer for a web application builder, in accordance with some implementations.

FIG. 5 shows an example of a dynamic page previewer for a web application with filter logic employed, in accordance with some implementations.

FIG. 6 shows a flowchart of an example of a method 600 for providing filter logic for a dynamic page previewer, performed in accordance with some implementations.

FIG. 7A shows a block diagram of an example of an environment 10 in which an on-demand database service can be used in accordance with some implementations.

FIG. 7B shows a block diagram of an example of some implementations of elements of FIG. 7A and various possible interconnections between these elements.

FIG. 8A shows a system diagram of an example of architectural components of an on-demand database service environment 900, in accordance with some implementations.

FIG. 8B shows a system diagram further illustrating an example of architectural components of an on-demand database service environment, in accordance with some implementations.

DETAILED DESCRIPTION

Examples of systems, apparatus, methods and computer program products according to the disclosed implementations are described in this section. These examples are being provided solely to add context and aid in the understanding of the disclosed implementations. It will thus be apparent to one skilled in the art that implementations may be practiced without some or all of these specific details. In other instances, certain operations have not been described in detail to avoid unnecessarily obscuring implementations. Other applications are possible, such that the following examples should not be taken as definitive or limiting either in scope or setting.

In the following detailed description, references are made to the accompanying drawings, which form a part of the description and in which are shown, by way of illustration, specific implementations. Although these implementations are described in sufficient detail to enable one skilled in the art to practice the disclosed implementations, it is understood that these examples are not limiting, such that other implementations may be used and changes may be made without departing from their spirit and scope. For example, the operations of methods shown and described herein are not necessarily performed in the order indicated. It should also be understood that the methods may include more or fewer operations than are indicated. In some implementations, operations described herein as separate operations may be combined. Conversely, what may be described herein as a single operation may be implemented in multiple operations.

Some implementations of the disclosed systems, apparatus, methods and computer program products are configured for providing a dynamic page previewer for a web application builder.

Web database environments that allow web applications to be presented to users directly within a browser or other web viewing experience are very popular for several reasons. They allow sophisticated web applications, connected to databases such as multi-tenant databases populated with many millions of records, to be deployed and presented to users on their devices effortlessly, without requiring any download or installation of the application locally. As such web application environments and frameworks gained in popularity, it became increasingly desirable for developers and companies to be able to create their own custom web applications and pages in such environments and frameworks. In some instances, “application builders” became available, allowing developers and non-developers (or “admins”) to create such applications and pages using a set of reusable building blocks. For example, a developer may be able to drag-and-drop page components such as a chat window or a clock widget onto a development area, with the application builder constructing a custom web application according to those specifications, with working chat window or clock widget as the developer requested.

While such application builders may provide a flexible set of reusable blocks for many application purposes, web applications using these components can quickly become complicated and sophisticated. Different users viewing these finished applications may see different components based on their permission to access components, their stated user preferences, conditions of whether a campaign has become large enough, or many other possibilities. Managing such applications with different users and conditions in mind can be hard for a developer to visualize and conceptualize.

By way of illustration, Acme is a company that uses a database environment called PureBuilder for designing sophisticated web experiences for its marketing campaigns. PureBuilder has a service called Application Builder that allows Acme to create applications, and Acme has done so to create a web front for its products using some simple building blocks provided in the Application Builder. However, Acme has standard customers and premium customers, and has designed their web front so that each type of customer sees completely different products and tools for searching those products. Unfortunately, Acme sees no easy way to preview the application so that the developers can quickly ascertain what a standard customer would see or a premium customer would see in a given page.

Some of the disclosed techniques can be implemented to provide a dynamic page previewer for a web application builder. In some implementations, the system maintains a multi-tenant database associated with a number of users, web applications, and web components. The system displays a user interface for the dynamic page previewer, consisting of a preview page of a web application that was built using a web application builder. The preview page shows web application components used in the web application, and component toggle buttons corresponding to the components. The system processes a user request to select a component toggle button, then determines visibility rules for the web application component that is selected for toggling. The system determines a visibility state for the component, then modifies the visibility states based on the component visibility rules. The preview page is then presented in the user interface, with the web application being visible or not visible according to the modified visibility state.

Some of the disclosed techniques can be implemented to provide filter logic for a dynamic page previewer. In some implementations, the dynamic page previewer is displayed in a user interface with web application components and component toggle buttons. A user request is processed to select a subset of the component toggle buttons, and component visibility rules are determined for the subset of component toggle buttons. The system determines a filter logic associated with the toggle buttons, and a visibility state for the component associated with the toggle buttons. The system then modifies the visibility state based on the one or more component visibility rules and the filter logic. Finally, the system presents the preview page in the user interface, with the component being visible or not visible based on the modified visibility state.

Applying some implementations of the disclosed techniques, an alternative scenario to that described above is provided. In this alternative scenario, Acme is able to see a dynamic preview page for the web front they have built with the Application Builder. The preview page initially shows all components for both standard and premium customers, but pre-configured toggle buttons allow Acme to determine rules for when premium components are displayed and when they're not. For example, a toggle button is marked “user status equals Premium”. By selecting this toggle button, the web application shows components as if a user with a status of Premium is viewing the web application. Therefore, the components marked Premium are viewable, while some standard components are not viewable. In addition, other toggle switches with a more sophisticated filter logic are available, and these allow components to be viewable or not viewable based on rules such as Button1 AND (Button2 OR Button3). This allows Acme to set up many scenarios for how pages are potentially viewable quite easily.

In some but not all implementations, the disclosed methods, apparatus, systems, and computer-readable storage media may be configured or designed for use in a multi-tenant database environment or system.

The term “multi-tenant database system” can refer to those systems in which various elements of hardware and software of a database system may be shared by one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows of data such as feed items for a potentially much greater number of customers. The term “query plan” generally refers to one or more operations used to access information in a database system.

FIG. 1 shows a system diagram of an example of a system 100 for providing a dynamic page previewer for a web application builder, in accordance with some implementations. System 100 includes a variety of different hardware and/or software components which are in communication with each other. In the non-limiting example of FIG. 1, system 100 includes at least one enterprise server 104, at least one client system 108, at least one multi-tenant database 112, and at least one component database 116.

Multi-tenant database 112 can allow for storage and retrieval of large sets of data. The multi-tenant database 112 can be a database implemented in HBase or other non-relational database management system. This database can include one or more records for each of a plurality of enterprises (also referred to as organizations, or tenants.) In some implementations, the database can include one or more shared tables, in which multiple enterprises have records in the same table, and share many of the same standard objects and columns for their records. In some implementations, each enterprise is associated with a tenant_id that provides unique identification for that particular enterprise in the multi-tenant database 112. For example, the entity Acme may have a tenant_id of “123” which uniquely identifies Acme as associated with a record or object. No other tenant within a shared table may have the same tenant_id. In some implementations, multi-tenant database 112 may store preview data for dynamic page previews of web applications.

Component database 116 is a database that stores a plurality of web components. In some implementations, the components are for use in web applications, web application builders, and/or web application builder frameworks. In some implementations, component database 116 may store one or more web application components, web application builder components, or both. In some implementations, component database 116 stores one or more pieces of metadata relating to the web components. In some implementations, component database 116 stores a metadata model for one or more of the web components. In some implementations, the metadata model is in tree structure, with the nodes of the tree consisting of attributes or properties of the web components.

Enterprise server 104 may communicate with other components of system 100. This communication may be facilitated through a combination of networks and interfaces. Enterprise server 104 may handle and process data requests from the client system 108. Likewise, enterprise server 104 may return a response to client system 108 after a data request has been processed. For example, enterprise server 104 may retrieve data from one or more databases, such as the multi-tenant database 112 or the component database 116. It may combine some or all of the data from different databases, and send the processed data to client system 108.

Client system 108 may be a computing device capable of communicating via one or more data networks with a server. Examples of client system 108 include a desktop computer or portable electronic device such as a smartphone, a tablet, a laptop, a wearable device such as Google Glass®, another optical head-mounted display (OHMD) device, a smart watch, etc. Client system 108 includes at least one browser in which applications may be deployed.

FIG. 2 shows a flowchart of an example of a method 200 for providing a dynamic page previewer for a web application builder, performed in accordance with some implementations. Method 200 and other methods described herein may be implemented using system 100 of FIG. 1, although the implementations of such methods are not limited to system 100.

At block 210, system 100 maintains a multi-tenant database 112 identifying web application components. In some implementations, the multi-tenant database 112 is shared by multiple enterprises. In some implementations, the multiple enterprises are each users of the system 100 and may be able to store and process data in the form of records. The records may be part of a shared table of the multi-tenant database 112. In some implementations, the web application components are configured to be reusable within a web application builder, and are further configured to construct web applications within the web application builder. In some implementations, one or more pieces of metadata may be stored in the multi-tenant database 112 in relation to the web application components. In some implementations, a metadata model may be stored for one or more of the web application components.

At block 220, system 100 displays a user interface for a dynamic page previewer for a server-hosted web application builder. In some implementations, the user interface includes a selectable list of a subset of the web application components. In some implementations, the user interface includes one or more “development areas”. Development areas represent a working area for the developers or admins constructing a web application. In some implementations, a development area allows for the placement of page or web application design elements, including the placement of web application components. In some implementations, the selectable list of web application components may be a palette. A palette shows all of the available web application components in a palette, toolbar, list, or other form of displaying the components.

In some implementations, the user interface includes or takes the form of a “preview page” of the web application. In some implementations, a preview page is a web page that constitutes a portion or interface of the web application. In some implementations, the preview page includes a number of web application components that are laid out on the page according to some arrangement. The preview page is intended to be a preview of work that a developer or administrator of the web application has done using the web application builder. In some implementations, the preview page includes one or more component toggle buttons that correspond to the number of web application components. In some implementations, component toggle buttons are user interface elements that have an on state and off state, or activated and inactivated state, that a user can toggle between. For example, a checkbox user interface element could be a component toggle button. In some implementations, the component toggle button is labeled or marked in some way, such as to denote a component name, a rule, a user, or other label associated with the component toggle button's functionality.

At block 230, system 100 processes a user request to select a component toggle button. In some implementations, the user request constitutes a user input that interacts with the component toggle button in some way. In some implementations, the user request constitutes a user input that switches a component toggle button from an activated to an inactivated state, or from an inactivated state to an activated state. For example, if the component toggle button is a checkbox, then a user may click on the checkbox to place a check or remove a check, thus toggling the component toggle button's on or off state. In some implementations, the user request is a user input within the user interface consisting of one or more clicks, touches, or selection gestures directed at the component toggle button.

At block 240, system 100 determines one or more component visibility rules associated with the web application component corresponding to the selected component toggle button. In some implementations, component visibility rules for a given web application component or for a given component toggle button may be retrieved from the multi-tenant database 112 or component database 116. In some implementations, component visibility rules may specify conditions for whether an associated web application component should be visible on a page of the web application or not. In some implementations, a developer or administrator of the web application can create or prepare component visibility rules to be associated with web application components. Examples of component visibility rules may include “NextStep NE Done”, designating that the variable NextStep's state must not equal to Done for the associated component to be visible; “ExpectedRevenue GT 100000”, designating that the variable ExpectedRevenue must be greater than 100,000 for the associated component to be visible; and any rule that might be imagined constituting a condition for component visibility.

In some implementations, one or more component visibility rules may involve determining that one or more users have permission to access the web application component. For example, a user without permission to view a specific component would not see the component, while a user with permission to view the specific component would. The component would be visible or not visible in the dynamic page previewer accordingly. In some implementations, one or more component visibility rules relate to one or more pieces of data from a user profile, user preferences section, or other user information associated with the user. In some implementations, one or more component visibility rules relate to one or more values of records in a database, such as multi-tenant database 112 or component database 116. In some implementations, the rules related to whether one or more records are equal to or above one or more designated threshold values. For example, “ExpectedRevenue GT 100000” would check if the ExpectedRevenue record is greater than the threshold value of 100,000.

At block 250, system 100 determines a visibility state for the web application component. In some implementations, the visibility state is metadata associated with the web application component. For example, the visibility state may take the form of a variable with an on or off state, such as Component.IsVisible=‘true’ or ‘false’. In some implementations, the visibility state depends on whether the component toggle button associated with the web application component is activated or inactivated. In some implementations, system 100 performs a check to determine whether the component visibility rule associated with the component toggle button is satisfied or the conditions are met.

At block 260, system 100 modifies the visibility state in relation to the component visibility rules. In some implementations, a visual marker of the component toggle button switching its state is shown. For example, an unmarked check box may be represented as a marked check box, signifying that the user in question has marked the check box. In some implementations, system 100 determines whether the component visibility rules would lead to the visibility state being changed based on the user request changing the component toggle button's state, where the component toggle button is tied to the component visibility rules for the web application component. In some implementations, system 100 switches the visibility state from inactivated to activated, or vice versa. For example, if a variable Component.IsVisible=‘false’, then system 100 modifies the visibility state such that Component.IsVisible=‘true’. In some implementations, a number of component visibility rules may function together to determine that the visibility state should be altered.

At block 270, system 100 presents the preview page with the web application component being visible or not visible based on the modified visibility state. If the visibility state has been modified to be inactivated, then system 100 removes the web application component from being visible on the preview page. If the visibility state has been modified to be activated, then system 100 adds the visible web application component to the preview page. In some implementations, the preview page is presented in real time, or substantially real time, after processing the first user request.

FIG. 3 shows an example of a web application builder, in accordance with some implementations. Example screenshot 300 shows a web application builder with a palette 310, canvas 320, and properties 330. In some implementations, the web application builder is presented to a user as a user interface that can be interacted with to construct web applications.

The palette 310 is a selectable list of one or more web application components that can be used and reused to construct web applications. For example, one of the web application components is “Rich Text”, which places a rich text field within the web application. Another component is “Chatter”, which places a social media component within the web application that can function such that the user can post to a social media service and perform other functions. In some implementations, the web application components can be presented as, or alongside, graphical representations indicating an object type or component type of the web application component. In some implementations, the web application components may be standard components, provided by default to users, or custom components that were created by or specifically for the user of the web application builder for use in building web applications.

The canvas 320 is an area where a user of the web application builder can design and lay out web applications or pages in a visual way. In some implementations, the user can drag one or more selectable components from the palette 310 into the canvas 320 to place them on the canvas. In some implementations, indications appear in areas of the canvas 320 where components may be placed.

The properties 330 is an area of the web application builder where users may view and modify one or more properties or attributes of a web application component or an object, either in the canvas 320, palette 310, or some other area of the web application builder. In some implementations, fields such as “Label”, “Developer Name”, “Page Type”, and more may designate the corresponding property or attribute, and one or more text fields of drop-down boxes may allow a user to modify attributes or properties. Various interactive elements, including buttons, may also appear to allow the user to view and/or modify properties of various aspects of web application components and objects.

FIG. 4 shows an example of a dynamic page previewer for a web application builder, in accordance with some implementations. The dynamic page previewer consists of a page or series of pages presented to the user of the web application builder, along the user to preview a web application in progress. Web application components 410, 420, 430, 440, and 450 appear within a preview page of the dynamic page previewer. Component 410 relates to an “Einstein” artificial intelligence component. A message notes that the permissions of the user are insufficient for displaying the component. Component 420 is a Chatter component for polls, questions, and posts in a social media service. Component 430 is a component for a social media service related to marketing campaigns and records. Component 440 shows an opportunity and related data for a marketing campaign. Component 450 shows the progress of an opportunity.

Component toggle buttons 460, 470, 475, 480, and 490 are toggle buttons in the form of checkboxes that are associated with components 410, 420, 430, 440, and 4450. Each component toggle button has a label designating that a component visibility rule is associated with the component toggle button. Button 460 is associated with the Einstein component 410, and is associated with a component visibility rule, wherein the Einstein component 410 is visible if the web application's user has “Opportunity IQ” enabled. Button 470 is associated with the Chatter component 420, and is associated with a rule where the component is visible only if the user can view Chatter pages. The component toggle buttons 475 are associated with visibility for a rich text component when either a variable called NextStep equals ‘Done’ or does not equal ‘Done’.

Component toggle buttons 480 work in tandem with a filter logic marked “1 OR 2”. When the component visibility rule associated with the first or second button is satisfied, the rich text component associated with them is visible. In this screenshot, the buttons are both activated, meaning both component visibility rules are simulated to be satisfied in the dynamic page previewer, so the component is visible. If either one or the other button is activated, the component would still be visible. The component is not visible only if both are not activated. Component toggle buttons 490 work in tandem with a filter logic marked “1 AND (2 OR 3)”. The filter logic of the first, second, and third buttons operate according to this filter logic to determine whether the associated component is visible. Here, all three buttons are activated, so the component is visible. If the first button was not activated, but the second and third were activated, then the component would not be visible.

FIG. 5 shows an example of a dynamic page previewer for a web application with filter logic employed, in accordance with some implementations. The example is the same as in FIG. 4, but with some different component toggle buttons activated. Component toggle buttons 530 are both activated. They correspond to the Einstein component 410 and the Chatter component 420, which are both visible because the component visibility rules are simulated to be satisfied in the dynamic page previewer. Component toggle buttons 540 have filter logic “1 OR 2”, meaning if either button is activated, then the component is visible. Here, neither button is activated, so the component is not visible. Component toggle buttons 550 have filter logic “1 AND (2 OR 3)”. Since the first button is not activated, the component is not visible. When comparing to FIG. 4, component 450 is no longer visible.

FIG. 6 shows a flowchart of an example of a method 600 for providing filter logic for a dynamic page previewer, performed in accordance with some implementations. Method 600 and other methods described herein may be implemented using system 100 of FIG. 1, although the implementations of such methods are not limited to system 100.

At block 610, system 100 maintains a multi-tenant database 112 identifying web application components. In some implementations, the multi-tenant database 112 is shared by multiple enterprises. In some implementations, the multiple enterprises are each users of the system 100 and may be able to store and process data in the form of records. The records may be part of a shared table of the multi-tenant database 112. In some implementations, the web application components are configured to be reusable within a web application builder, and are further configured to construct web applications within the web application builder. In some implementations, one or more pieces of metadata may be stored in the multi-tenant database 112 in relation to the web application components. In some implementations, a metadata model may be stored for one or more of the web application components.

At block 620, system 100 displays a user interface for a dynamic page previewer for a server-hosted web application builder. In some implementations, the user interface includes a selectable list of a subset of the web application components. In some implementations, the user interface includes one or more “development areas”. Development areas represent a working area for the developers or admins constructing a web application. In some implementations, a development area allows for the placement of page or web application design elements, including the placement of web application components. In some implementations, the selectable list of web application components may be a palette. A palette shows all of the available web application components in a palette, toolbar, list, or other form of displaying the components.

In some implementations, the user interface includes or takes the form of a “preview page” of the web application. In some implementations, a preview page is a web page that constitutes a portion or interface of the web application. In some implementations, the preview page includes a number of web application components that are laid out on the page according to some arrangement. The preview page is intended to be a preview of work that a developer or administrator of the web application has done using the web application builder. In some implementations, the preview page includes one or more component toggle buttons that correspond to the number of web application components. In some implementations, component toggle buttons are user interface elements that have an on state and off state, or activated and inactivated state, that a user can toggle between. For example, a checkbox user interface element could be a component toggle button. In some implementations, the component toggle button is labeled or marked in some way, such as to denote a component name, a rule, a user, or other label associated with the component toggle button's functionality.

At block 630, system 100 processes a user request to select a subset of the component toggle buttons. In some implementations, the user request constitutes a user input that interacts with the subset of component toggle buttons in some way. In some implementations, the user request constitutes a user input that switches one or more component toggle buttons from an activated to an inactivated state, or from an inactivated state to an activated state. For example, if the component toggle button is a checkbox, then a user may click on the checkbox to place a check or remove a check, thus toggling the component toggle button's on or off state. In some implementations, the user request is a user input within the user interface consisting of one or more clicks, touches, or selection gestures directed at the component toggle button.

At block 640, system 100 determines one or more component visibility rules associated with the subset of component toggle buttons. In some implementations, component visibility rules for a given component toggle button may be retrieved from the multi-tenant database 112 or component database 116. In some implementations, component visibility rules may specify conditions for whether an associated web application component should be visible on a page of the web application or not. In some implementations, a developer or administrator of the web application can create or prepare component visibility rules to be associated with web application components. Examples of component visibility rules may include “NextStep NE Done”, designating that the variable NextStep's state must not equal to Done for the associated component to be visible; “ExpectedRevenue GT 100000”, designating that the variable ExpectedRevenue must be greater than 100,000 for the associated component to be visible; and any rule that might be imagined constituting a condition for component visibility.

In some implementations, one or more component visibility rules may involve determining that one or more users have permission to access the web application component. For example, a user without permission to view a specific component would not see the component, while a user with permission to view the specific component would. The component would be visible or not visible in the dynamic page previewer accordingly. In some implementations, one or more component visibility rules relate to one or more pieces of data from a user profile, user preferences section, or other user information associated with the user. In some implementations, one or more component visibility rules relate to one or more values of records in a database, such as multi-tenant database 112 or component database 116. In some implementations, the rules related to whether one or more records are equal to or above one or more designated threshold values. For example, “ExpectedRevenue GT 100000” would check if the ExpectedRevenue record is greater than the threshold value of 100,000.

At block 650, system 100 determines a filter logic associated with the subset of component toggle buttons. In some implementations, a filter logic relates to two or more component toggle buttons and the associated web application component for those component toggle buttons. The filter logic can include a logical statement involving one or more AND or OR conditions for the subset of component toggle buttons, such as “1 OR 2”, or “1 AND (2 OR 3)”. The number relates to the component toggle buttons and their activation states. If the first component toggle button is activated, for example, then the state is “1”. If both the first and second component toggle buttons are activated, then the state is “1 AND 2”, and so on. In some implementations, system 100 retrieves the filter logic from multi-tenant database 112 or the component database 116. In some implementations, the filter logic involves at least one nested AND or OR condition for the subset of component toggle buttons.

At block 660, system 100 determines a visibility state for the web application component. In some implementations, the visibility state is metadata associated with the web application component. For example, the visibility state may take the form of a variable with an on or off state, such as Component.IsVisible=‘true’ or ‘false’. In some implementations, the visibility state depends on whether the component toggle button associated with the web application component is activated or inactivated. In some implementations, system 100 performs a check to determine whether the component visibility rule associated with the component toggle button is satisfied or the conditions are met.

At block 670, system 100 modifies the visibility state in relation to the component visibility rules and the filter logic. In some implementations, modifying the visibility state involves at least satisfying one or more conditions of the filter logic with respect to the subset of component toggle buttons. In some implementations, a visual marker of the component toggle button or buttons switching their states are shown. For example, an unmarked check box may be represented as a marked check box, signifying that the user in question has marked the check box. In some implementations, system 100 determines whether the component visibility rules and the filter logic would lead to the visibility state being changed based on the user request changing the component toggle button's state, where the component toggle button is tied to the component visibility rules and the filter logic for the web application component. In some implementations, system 100 switches the visibility state from inactivated to activated, or vice versa. For example, if a variable Component.IsVisible=‘false’, then system 100 modifies the visibility state such that Component.IsVisible=‘true’. In some implementations, a number of component visibility rules may function together to determine that the visibility state should be altered, based on the chain of logic set up in the filter logic.

At block 680, system 100 presents the preview page with the web application component being visible or not visible based on the modified visibility state. If the visibility state has been modified to be inactivated, then system 100 removes the web application component from being visible on the preview page. If the visibility state has been modified to be activated, then system 100 adds the visible web application component to the preview page. In some implementations, the preview page is presented in real time, or substantially real time, after processing the first user request.

Systems, apparatus, and methods are described below for implementing database systems and enterprise level social and business information networking systems in conjunction with the disclosed techniques. Such implementations can provide more efficient use of a database system. For instance, a user of a database system may not easily know when important information in the database has changed, e.g., about a project or client. Such implementations can provide feed tracked updates about such changes and other events, thereby keeping users informed.

By way of example, a user can update a record in the form of a CRM record, e.g., an opportunity such as a possible sale of 1000 computers. Once the record update has been made, a feed tracked update about the record update can then automatically be provided, e.g., in a feed, to anyone subscribing to the opportunity or to the user. Thus, the user does not need to contact a manager regarding the change in the opportunity, since the feed tracked update about the update is sent via a feed to the manager's feed page or other page.

FIG. 7A shows a block diagram of an example of an environment 10 in which an on-demand database service exists and can be used in accordance with some implementations. Environment 10 may include user systems 12, network 14, database system 16, processor system 17, application platform 18, network interface 20, tenant data storage 22, system data storage 24, program code 26, and process space 28. In other implementations, environment 10 may not have all of these components and/or may have other components instead of, or in addition to, those listed above.

A user system 12 may be implemented as any computing device(s) or other data processing apparatus such as a machine or system used by a user to access a database system 16. For example, any of user systems 12 can be a handheld and/or portable computing device such as a mobile phone, a smartphone, a laptop computer, or a tablet. Other examples of a user system include computing devices such as a work station and/or a network of computing devices. As illustrated in FIG. 7A (and in more detail in FIG. 7B) user systems 12 might interact via a network 14 with an on-demand database service, which is implemented in the example of FIG. 7A as database system 16.

An on-demand database service, implemented using system 16 by way of example, is a service that is made available to users who do not need to necessarily be concerned with building and/or maintaining the database system. Instead, the database system may be available for their use when the users need the database system, i.e., on the demand of the users. Some on-demand database services may store information from one or more tenants into tables of a common database image to form a multi-tenant database system (MTS). A database image may include one or more database objects. A relational database management system (RDBMS) or the equivalent may execute storage and retrieval of information against the database object(s). A non-relational database management system (NRDBMS) or the equivalent may execute storage and fast retrieval of large sets of information against the database object(s). Application platform 18 may be a framework that allows the applications of system 16 to run, such as the hardware and/or software, e.g., the operating system. In some implementations, application platform 18 enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 12, or third party application developers accessing the on-demand database service via user systems 12.

The users of user systems 12 may differ in their respective capacities, and the capacity of a particular user system 12 might be entirely determined by permissions (permission levels) for the current user. For example, when a salesperson is using a particular user system 12 to interact with system 16, the user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 16, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level, also called authorization.

Network 14 is any network or combination of networks of devices that communicate with one another. For example, network 14 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. Network 14 can include a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the Internet. The Internet will be used in many of the examples herein. However, it should be understood that the networks that the present implementations might use are not so limited.

User systems 12 might communicate with system 16 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, user system 12 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP signals to and from an HTTP server at system 16. Such an HTTP server might be implemented as the sole network interface 20 between system 16 and network 14, but other techniques might be used as well or instead. In some implementations, the network interface 20 between system 16 and network 14 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least for users accessing system 16, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.

In one implementation, system 16, shown in FIG. 7A, implements a web-based CRM system. For example, in one implementation, system 16 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, web pages and other information to and from user systems 12 and to store to, and retrieve from, a database system related data, objects, and Webpage content. With a multi-tenant system, data for multiple tenants may be stored in the same physical database object in tenant data storage 22, however, tenant data typically is arranged in the storage medium(s) of tenant data storage 22 so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data, unless such data is expressly shared. In certain implementations, system 16 implements applications other than, or in addition to, a CRM application. For example, system 16 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application. User (or third party developer) applications, which may or may not include CRM, may be supported by the application platform 18, which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of the system 16.

One arrangement for elements of system 16 is shown in FIGS. 7A and 7B, including a network interface 20, application platform 18, tenant data storage 22 for tenant data 23, system data storage 24 for system data 25 accessible to system 16 and possibly multiple tenants, program code 26 for implementing various functions of system 16, and a process space 28 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system 16 include database indexing processes.

Several elements in the system shown in FIG. 7A include conventional, well-known elements that are explained only briefly here. For example, each user system 12 could include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection. The term “computing device” is also referred to herein simply as a “computer”. User system 12 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) of user system 12 to access, process and view information, pages and applications available to it from system 16 over network 14. Each user system 12 also typically includes one or more user input devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a GUI provided by the browser on a display (e.g., a monitor screen, LCD display, OLED display, etc.) of the computing device in conjunction with pages, forms, applications and other information provided by system 16 or other systems or servers. Thus, “display device” as used herein can refer to a display of a computer system such as a monitor or touch-screen display, and can refer to any computing device having display capabilities such as a desktop computer, laptop, tablet, smartphone, a television set-top box, or wearable device such Google Glass® or other human body-mounted display apparatus. For example, the display device can be used to access data and applications hosted by system 16, and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user. As discussed above, implementations are suitable for use with the Internet, although other networks can be used instead of or in addition to the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one implementation, each user system 12 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 16 (and additional instances of an MTS, where more than one is present) and all of its components might be operator configurable using application(s) including computer code to run using processor system 17, which may be implemented to include a central processing unit, which may include an Intel Pentium® processor or the like, and/or multiple processor units. Non-transitory computer-readable media can have instructions stored thereon/in, that can be executed by or used to program a computing device to perform any of the methods of the implementations described herein. Computer program code 26 implementing instructions for operating and configuring system 16 to intercommunicate and to process web pages, applications and other data and media content as described herein is preferably downloadable and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any other type of computer-readable medium or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for the disclosed implementations can be realized in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.).

According to some implementations, each system 16 is configured to provide web pages, forms, applications, data and media content to user (client) systems 12 to support the access by user systems 12 as tenants of system 16. As such, system 16 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to refer to one type of computing device such as a system including processing hardware and process space(s), an associated storage medium such as a memory device or database, and, in some instances, a database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database objects described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.

FIG. 7B shows a block diagram of an example of some implementations of elements of FIG. 7A and various possible interconnections between these elements. That is, FIG. 7B also illustrates environment 10. However, in FIG. 7B elements of system 16 and various interconnections in some implementations are further illustrated. FIG. 7B shows that user system 12 may include processor system 8A, memory system 8B, input system 12C, and output system 12D. FIG. 7B shows network 14 and system 16. FIG. 7B also shows that system 16 may include tenant data storage 22, tenant data 23, system data storage 24, system data 25, User Interface (UI) 30, Application Program Interface (API) 32, PL/SOQL 34, save routines 36, application setup mechanism 38, application servers 50 ₁-50 _(N), system process space 52, tenant process spaces 54, tenant management process space 60, tenant storage space 62, user storage 64, and application metadata 66. In other implementations, environment 10 may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above.

User system 12, network 14, system 16, tenant data storage 22, and system data storage 24 were discussed above in FIG. 7A. Regarding user system 12, processor system 8A may be any combination of one or more processors. Memory system 8B may be any combination of one or more memory devices, short term, and/or long term memory. Input system 12C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks. Output system 12D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks. As shown by FIG. 7B, system 16 may include a network interface 20 (of FIG. 7A) implemented as a set of application servers 50, an application platform 18, tenant data storage 22, and system data storage 24. Also shown is system process space 52, including individual tenant process spaces 54 and a tenant management process space 60. Each application server 50 may be configured to communicate with tenant data storage 22 and the tenant data 23 therein, and system data storage 24 and the system data 25 therein to serve requests of user systems 12. The tenant data 23 might be divided into individual tenant storage spaces 62, which can be either a physical arrangement and/or a logical arrangement of data. Within each tenant storage space 62, user storage 64 and application metadata 66 might be similarly allocated for each user. For example, a copy of a user's most recently used (MRU) items might be stored to user storage 64. Similarly, a copy of MRU items for an entire organization that is a tenant might be stored to tenant storage space 62. A UI 30 provides a user interface and an API 32 provides an application programmer interface to system 16 resident processes to users and/or developers at user systems 12. The tenant data and the system data may be stored in various databases, such as one or more Oracle® databases.

Application platform 18 includes an application setup mechanism 38 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 22 by save routines 36 for execution by subscribers as one or more tenant process spaces 54 managed by tenant management process 60 for example. Invocations to such applications may be coded using PL/SOQL 34 that provides a programming language style interface extension to API 32. A detailed description of some PL/SOQL language implementations is discussed in commonly assigned U.S. Pat. No. 7,730,478, titled METHOD AND SYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA A MULTI-TENANT ON-DEMAND DATABASE SERVICE, by Craig Weissman, issued on Jun. 1, 2010, and hereby incorporated by reference in its entirety and for all purposes. Invocations to applications may be detected by one or more system processes, which manage retrieving application metadata 66 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.

Each application server 50 may be communicably coupled to database systems, e.g., having access to system data 25 and tenant data 23, via a different network connection. For example, one application server 50 ₁ might be coupled via the network 14 (e.g., the Internet), another application server 50 _(N-1) might be coupled via a direct network link, and another application server 50 _(N) might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers 50 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.

In certain implementations, each application server 50 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 50. In one implementation, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 50 and the user systems 12 to distribute requests to the application servers 50. In one implementation, the load balancer uses a least connections algorithm to route user requests to the application servers 50. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain implementations, three consecutive requests from the same user could hit three different application servers 50, and three requests from different users could hit the same application server 50. In this manner, by way of example, system 16 is multi-tenant, wherein system 16 handles storage of, and access to, different objects, data and applications across disparate users and organizations.

As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses system 16 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 22). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by system 16 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant-specific data, system 16 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.

In certain implementations, user systems 12 (which may be client systems) communicate with application servers 50 to request and update system-level and tenant-level data from system 16 that may involve sending one or more queries to tenant data storage 22 and/or system data storage 24. System 16 (e.g., an application server 50 in system 16) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. System data storage 24 may generate query plans to access the requested data from the database.

Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories. A “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects according to some implementations. It should be understood that “table” and “object” may be used interchangeably herein. Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc. In some multi-tenant database systems, standard entity tables might be provided for use by all tenants. For CRM database applications, such standard entities might include tables for case, account, contact, lead, and opportunity data objects, each containing pre-defined fields. It should be understood that the word “entity” may also be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. Commonly assigned U.S. Pat. No. 7,779,039, titled CUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASE SYSTEM, by Weissman et al., issued on Aug. 17, 2010, and hereby incorporated by reference in its entirety and for all purposes, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system. In certain implementations, for example, all custom entity data rows are stored in a single multi-tenant physical table, which may contain multiple logical tables per organization. It is transparent to customers that their multiple “tables” are in fact stored in one large table or that their data may be stored in the same table as the data of other customers.

FIG. 8A shows a system diagram of an example of architectural components of an on-demand database service environment 900, in accordance with some implementations. A client machine located in the cloud 904, generally referring to one or more networks in combination, as described herein, may communicate with the on-demand database service environment via one or more edge routers 908 and 912. A client machine can be any of the examples of user systems 12 described above. The edge routers may communicate with one or more core switches 920 and 924 via firewall 916. The core switches may communicate with a load balancer 928, which may distribute server load over different pods, such as the pods 940 and 944. The pods 940 and 944, which may each include one or more servers and/or other computing resources, may perform data processing and other operations used to provide on-demand services. Communication with the pods may be conducted via pod switches 932 and 936. Components of the on-demand database service environment may communicate with a database storage 956 via a database firewall 948 and a database switch 952.

As shown in FIGS. 8A and 8B, accessing an on-demand database service environment may involve communications transmitted among a variety of different hardware and/or software components. Further, the on-demand database service environment 900 is a simplified representation of an actual on-demand database service environment. For example, while only one or two devices of each type are shown in FIGS. 8A and 8B, some implementations of an on-demand database service environment may include anywhere from one to many devices of each type. Also, the on-demand database service environment need not include each device shown in FIGS. 8A and 8B, or may include additional devices not shown in FIGS. 8A and 8B.

Moreover, one or more of the devices in the on-demand database service environment 900 may be implemented on the same physical device or on different hardware. Some devices may be implemented using hardware or a combination of hardware and software. Thus, terms such as “data processing apparatus,” “machine,” “server” and “device” as used herein are not limited to a single hardware device, but rather include any hardware and software configured to provide the described functionality.

The cloud 904 is intended to refer to a data network or combination of data networks, often including the Internet. Client machines located in the cloud 904 may communicate with the on-demand database service environment to access services provided by the on-demand database service environment. For example, client machines may access the on-demand database service environment to retrieve, store, edit, and/or process information.

In some implementations, the edge routers 908 and 912 route packets between the cloud 904 and other components of the on-demand database service environment 900. The edge routers 908 and 912 may employ the Border Gateway Protocol (BGP). The BGP is the core routing protocol of the Internet. The edge routers 908 and 912 may maintain a table of IP networks or ‘prefixes’, which designate network reachability among autonomous systems on the Internet.

In one or more implementations, the firewall 916 may protect the inner components of the on-demand database service environment 900 from Internet traffic. The firewall 916 may block, permit, or deny access to the inner components of the on-demand database service environment 900 based upon a set of rules and other criteria. The firewall 916 may act as one or more of a packet filter, an application gateway, a stateful filter, a proxy server, or any other type of firewall.

In some implementations, the core switches 920 and 924 are high-capacity switches that transfer packets within the on-demand database service environment 900. The core switches 920 and 924 may be configured as network bridges that quickly route data between different components within the on-demand database service environment. In some implementations, the use of two or more core switches 920 and 924 may provide redundancy and/or reduced latency.

In some implementations, the pods 940 and 944 may perform the core data processing and service functions provided by the on-demand database service environment. Each pod may include various types of hardware and/or software computing resources. An example of the pod architecture is discussed in greater detail with reference to FIG. 8B.

In some implementations, communication between the pods 940 and 944 may be conducted via the pod switches 932 and 936. The pod switches 932 and 936 may facilitate communication between the pods 940 and 944 and client machines located in the cloud 904, for example via core switches 920 and 924. Also, the pod switches 932 and 936 may facilitate communication between the pods 940 and 944 and the database storage 956.

In some implementations, the load balancer 928 may distribute workload between the pods 940 and 944. Balancing the on-demand service requests between the pods may assist in improving the use of resources, increasing throughput, reducing response times, and/or reducing overhead. The load balancer 928 may include multilayer switches to analyze and forward traffic.

In some implementations, access to the database storage 956 may be guarded by a database firewall 948. The database firewall 948 may act as a computer application firewall operating at the database application layer of a protocol stack. The database firewall 948 may protect the database storage 956 from application attacks such as structure query language (SQL) injection, database rootkits, and unauthorized information disclosure.

In some implementations, the database firewall 948 may include a host using one or more forms of reverse proxy services to proxy traffic before passing it to a gateway router. The database firewall 948 may inspect the contents of database traffic and block certain content or database requests. The database firewall 948 may work on the SQL application level atop the TCP/IP stack, managing applications' connection to the database or SQL management interfaces as well as intercepting and enforcing packets traveling to or from a database network or application interface.

In some implementations, communication with the database storage 956 may be conducted via the database switch 952. The multi-tenant database storage 956 may include more than one hardware and/or software components for handling database queries. Accordingly, the database switch 952 may direct database queries transmitted by other components of the on-demand database service environment (e.g., the pods 940 and 944) to the correct components within the database storage 956.

In some implementations, the database storage 956 is an on-demand database system shared by many different organizations. The on-demand database service may employ a multi-tenant approach, a virtualized approach, or any other type of database approach. On-demand database services are discussed in greater detail with reference to FIGS. 8A and 8B.

FIG. 8B shows a system diagram further illustrating an example of architectural components of an on-demand database service environment, in accordance with some implementations. The pod 944 may be used to render services to a user of the on-demand database service environment 900. In some implementations, each pod may include a variety of servers and/or other systems. The pod 944 includes one or more content batch servers 964, content search servers 968, query servers 982, file servers 986, access control system (ACS) servers 980, batch servers 984, and app servers 988. Also, the pod 944 includes database instances 990, quick file systems (QFS) 992, and indexers 994. In one or more implementations, some or all communication between the servers in the pod 944 may be transmitted via the switch 936.

The content batch servers 964 may handle requests internal to the pod. These requests may be long-running and/or not tied to a particular customer. For example, the content batch servers 964 may handle requests related to log mining, cleanup work, and maintenance tasks.

The content search servers 968 may provide query and indexer functions. For example, the functions provided by the content search servers 968 may allow users to search through content stored in the on-demand database service environment.

The file servers 986 may manage requests for information stored in the file storage 998. The file storage 998 may store information such as documents, images, and basic large objects (BLOBs). By managing requests for information using the file servers 986, the image footprint on the database may be reduced.

The query servers 982 may be used to retrieve information from one or more file systems. For example, the query system 982 may receive requests for information from the app servers 988 and then transmit information queries to the NFS 996 located outside the pod.

The pod 944 may share a database instance 990 configured as a multi-tenant environment in which different organizations share access to the same database. Additionally, services rendered by the pod 944 may call upon various hardware and/or software resources. In some implementations, the ACS servers 980 may control access to data, hardware resources, or software resources.

In some implementations, the batch servers 984 may process batch jobs, which are used to run tasks at specified times. Thus, the batch servers 984 may transmit instructions to other servers, such as the app servers 988, to trigger the batch jobs.

In some implementations, the QFS 992 may be an open source file system available from Sun Microsystems® of Santa Clara, Calif. The QFS may serve as a rapid-access file system for storing and accessing information available within the pod 944. The QFS 992 may support some volume management capabilities, allowing many disks to be grouped together into a file system. File system metadata can be kept on a separate set of disks, which may be useful for streaming applications where long disk seeks cannot be tolerated. Thus, the QFS system may communicate with one or more content search servers 968 and/or indexers 994 to identify, retrieve, move, and/or update data stored in the network file systems 996 and/or other storage systems.

In some implementations, one or more query servers 982 may communicate with the NFS 996 to retrieve and/or update information stored outside of the pod 944. The NFS 996 may allow servers located in the pod 944 to access information to access files over a network in a manner similar to how local storage is accessed.

In some implementations, queries from the query servers 922 may be transmitted to the NFS 996 via the load balancer 928, which may distribute resource requests over various resources available in the on-demand database service environment. The NFS 996 may also communicate with the QFS 992 to update the information stored on the NFS 996 and/or to provide information to the QFS 992 for use by servers located within the pod 944.

In some implementations, the pod may include one or more database instances 990. The database instance 990 may transmit information to the QFS 992. When information is transmitted to the QFS, it may be available for use by servers within the pod 944 without using an additional database call.

In some implementations, database information may be transmitted to the indexer 994. Indexer 994 may provide an index of information available in the database 990 and/or QFS 992. The index information may be provided to file servers 986 and/or the QFS 992.

Some but not all of the techniques described or referenced herein are implemented as part of or in conjunction with a social networking database system, also referred to herein as a social networking system or as a social network. Social networking systems have become a popular way to facilitate communication among people, any of whom can be recognized as users of a social networking system. One example of a social networking system is Chatter®, provided by salesforce.com, inc. of San Francisco, Calif. salesforce.com, inc. is a provider of social networking services, CRM services and other database management services, any of which can be accessed and used in conjunction with the techniques disclosed herein in some implementations. These various services can be provided in a cloud computing environment, for example, in the context of a multi-tenant database system. Thus, the disclosed techniques can be implemented without having to install software locally, that is, on computing devices of users interacting with services available through the cloud. While the disclosed implementations are often described with reference to Chatter®, those skilled in the art should understand that the disclosed techniques are neither limited to Chatter® nor to any other services and systems provided by salesforce.com, inc. and can be implemented in the context of various other database systems and/or social networking systems such as Facebook®, LinkedIn®, Twitter®, Google+®, Yammer® and Jive® by way of example only.

Some social networking systems can be implemented in various settings, including organizations. For instance, a social networking system can be implemented to connect users within an enterprise such as a company or business partnership, or a group of users within such an organization. For instance, Chatter® can be used by employee users in a division of a business organization to share data, communicate, and collaborate with each other for various social purposes often involving the business of the organization. In the example of a multi-tenant database system, each organization or group within the organization can be a respective tenant of the system, as described in greater detail herein.

In some social networking systems, users can access one or more social network feeds, which include information updates presented as items or entries in the feed. Such a feed item can include a single information update or a collection of individual information updates. A feed item can include various types of data including character-based data, audio data, image data and/or video data. A social network feed can be displayed in a graphical user interface (GUI) on a display device such as the display of a computing device as described herein. The information updates can include various social network data from various sources and can be stored in an on-demand database service environment. In some implementations, the disclosed methods, apparatus, systems, and computer-readable storage media may be configured or designed for use in a multi-tenant database environment.

In some implementations, a social networking system may allow a user to follow data objects in the form of CRM records such as cases, accounts, or opportunities, in addition to following individual users and groups of users. The “following” of a record stored in a database, as described in greater detail herein, allows a user to track the progress of that record when the user is subscribed to the record. Updates to the record, also referred to herein as changes to the record, are one type of information update that can occur and be noted on a social network feed such as a record feed or a news feed of a user subscribed to the record. Examples of record updates include field changes in the record, updates to the status of a record, as well as the creation of the record itself. Some records are publicly accessible, such that any user can follow the record, while other records are private, for which appropriate security clearance/permissions are a prerequisite to a user following the record.

Information updates can include various types of updates, which may or may not be linked with a particular record. For example, information updates can be social media messages submitted by a user or can otherwise be generated in response to user actions or in response to events. Examples of social media messages include: posts, comments, indications of a user's personal preferences such as “likes” and “dislikes”, updates to a user's status, uploaded files, and user-submitted hyperlinks to social network data or other network data such as various documents and/or web pages on the Internet. Posts can include alpha-numeric or other character-based user inputs such as words, phrases, statements, questions, emotional expressions, and/or symbols. Comments generally refer to responses to posts or to other information updates, such as words, phrases, statements, answers, questions, and reactionary emotional expressions and/or symbols. Multimedia data can be included in, linked with, or attached to a post or comment. For example, a post can include textual statements in combination with a JPEG image or animated image. A like or dislike can be submitted in response to a particular post or comment. Examples of uploaded files include presentations, documents, multimedia files, and the like.

Users can follow a record by subscribing to the record, as mentioned above. Users can also follow other entities such as other types of data objects, other users, and groups of users. Feed tracked updates regarding such entities are one type of information update that can be received and included in the user's news feed. Any number of users can follow a particular entity and thus view information updates pertaining to that entity on the users' respective news feeds. In some social networks, users may follow each other by establishing connections with each other, sometimes referred to as “friending” one another. By establishing such a connection, one user may be able to see information generated by, generated about, or otherwise associated with another user. For instance, a first user may be able to see information posted by a second user to the second user's personal social network page. One implementation of such a personal social network page is a user's profile page, for example, in the form of a web page representing the user's profile. In one example, when the first user is following the second user, the first user's news feed can receive a post from the second user submitted to the second user's profile feed. A user's profile feed is also referred to herein as the user's “wall,” which is one example of a social network feed displayed on the user's profile page.

In some implementations, a social network feed may be specific to a group of users of a social networking system. For instance, a group of users may publish a news feed. Members of the group may view and post to this group feed in accordance with a permissions configuration for the feed and the group. Information updates in a group context can also include changes to group status information.

In some implementations, when data such as posts or comments input from one or more users are submitted to a social network feed for a particular user, group, object, or other construct within a social networking system, an email notification or other type of network communication may be transmitted to all users following the user, group, or object in addition to the inclusion of the data as a feed item in one or more feeds, such as a user's profile feed, a news feed, or a record feed. In some social networking systems, the occurrence of such a notification is limited to the first instance of a published input, which may form part of a larger conversation. For instance, a notification may be transmitted for an initial post, but not for comments on the post. In some other implementations, a separate notification is transmitted for each such information update.

The term “multi-tenant database system” generally refers to those systems in which various elements of hardware and/or software of a database system may be shared by one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows of data such as feed items for a potentially much greater number of customers.

An example of a “user profile” or “user's profile” is a database object or set of objects configured to store and maintain data about a given user of a social networking system and/or database system. The data can include general information, such as name, title, phone number, a photo, a biographical summary, and a status, e.g., text describing what the user is currently doing. As mentioned herein, the data can include social media messages created by other users. Where there are multiple tenants, a user is typically associated with a particular tenant. For example, a user could be a salesperson of a company, which is a tenant of the database system that provides a database service.

The term “record” generally refers to a data entity having fields with values and stored in database system. An example of a record is an instance of a data object created by a user of the database service, for example, in the form of a CRM record about a particular (actual or potential) business relationship or project. The record can have a data structure defined by the database service (a standard object) or defined by a user (custom object). For example, a record can be for a business partner or potential business partner (e.g., a client, vendor, distributor, etc.) of the user, and can include information describing an entire company, subsidiaries, or contacts at the company. As another example, a record can be a project that the user is working on, such as an opportunity (e.g., a possible sale) with an existing partner, or a project that the user is trying to get. In one implementation of a multi-tenant database system, each record for the tenants has a unique identifier stored in a common table. A record has data fields that are defined by the structure of the object (e.g., fields of certain data types and purposes). A record can also have custom fields defined by a user. A field can be another record or include links thereto, thereby providing a parent-child relationship between the records.

The terms “social network feed” and “feed” are used interchangeably herein and generally refer to a combination (e.g., a list) of feed items or entries with various types of information and data. Such feed items can be stored and maintained in one or more database tables, e.g., as rows in the table(s), that can be accessed to retrieve relevant information to be presented as part of a displayed feed. The term “feed item” (or feed element) generally refers to an item of information, which can be presented in the feed such as a post submitted by a user. Feed items of information about a user can be presented in a user's profile feed of the database, while feed items of information about a record can be presented in a record feed in the database, by way of example. A profile feed and a record feed are examples of different types of social network feeds. A second user following a first user and a record can receive the feed items associated with the first user and the record for display in the second user's news feed, which is another type of social network feed. In some implementations, the feed items from any number of followed users and records can be combined into a single social network feed of a particular user.

As examples, a feed item can be a social media message, such as a user-generated post of text data, and a feed tracked update to a record or profile, such as a change to a field of the record. Feed tracked updates are described in greater detail herein. A feed can be a combination of social media messages and feed tracked updates. Social media messages include text created by a user, and may include other data as well. Examples of social media messages include posts, user status updates, and comments. Social media messages can be created for a user's profile or for a record. Posts can be created by various users, potentially any user, although some restrictions can be applied. As an example, posts can be made to a wall section of a user's profile page (which can include a number of recent posts) or a section of a record that includes multiple posts. The posts can be organized in chronological order when displayed in a GUI, for instance, on the user's profile page, as part of the user's profile feed. In contrast to a post, a user status update changes a status of a user and can be made by that user or an administrator. A record can also have a status, the update of which can be provided by an owner of the record or other users having suitable write access permissions to the record. The owner can be a single user, multiple users, or a group.

In some implementations, a comment can be made on any feed item. In some implementations, comments are organized as a list explicitly tied to a particular feed tracked update, post, or status update. In some implementations, comments may not be listed in the first layer (in a hierarchal sense) of feed items, but listed as a second layer branching from a particular first layer feed item.

A “feed tracked update,” also referred to herein as a “feed update,” is one type of information update and generally refers to data representing an event. A feed tracked update can include text generated by the database system in response to the event, to be provided as one or more feed items for possible inclusion in one or more feeds. In one implementation, the data can initially be stored, and then the database system can later use the data to create text for describing the event. Both the data and/or the text can be a feed tracked update, as used herein. In various implementations, an event can be an update of a record and/or can be triggered by a specific action by a user. Which actions trigger an event can be configurable. Which events have feed tracked updates created and which feed updates are sent to which users can also be configurable. Social media messages and other types of feed updates can be stored as a field or child object of the record. For example, the feed can be stored as a child object of the record.

A “group” is generally a collection of users. In some implementations, the group may be defined as users with a same or similar attribute, or by membership. In some implementations, a “group feed”, also referred to herein as a “group news feed”, includes one or more feed items about any user in the group. In some implementations, the group feed also includes information updates and other feed items that are about the group as a whole, the group's purpose, the group's description, and group records and other objects stored in association with the group. Threads of information updates including group record updates and social media messages, such as posts, comments, likes, etc., can define group conversations and change over time.

An “entity feed” or “record feed” generally refers to a feed of feed items about a particular record in the database. Such feed items can include feed tracked updates about changes to the record and posts made by users about the record. An entity feed can be composed of any type of feed item. Such a feed can be displayed on a page such as a web page associated with the record, e.g., a home page of the record. As used herein, a “profile feed” or “user's profile feed” generally refers to a feed of feed items about a particular user. In one example, the feed items for a profile feed include posts and comments that other users make about or send to the particular user, and status updates made by the particular user. Such a profile feed can be displayed on a page associated with the particular user. In another example, feed items in a profile feed could include posts made by the particular user and feed tracked updates initiated based on actions of the particular user.

While some of the disclosed implementations may be described with reference to a system having an application server providing a front end for an on-demand database service capable of supporting multiple tenants, the disclosed implementations are not limited to multi-tenant databases nor deployment on application servers. Some implementations may be practiced using various database architectures such as ORACLE®, DB2® by IBM and the like without departing from the scope of the implementations claimed.

It should be understood that some of the disclosed implementations can be embodied in the form of control logic using hardware and/or computer software in a modular or integrated manner. Other ways and/or methods are possible using hardware and a combination of hardware and software.

Any of the disclosed implementations may be embodied in various types of hardware, software, firmware, and combinations thereof. For example, some techniques disclosed herein may be implemented, at least in part, by computer-readable media that include program instructions, state information, etc., for performing various services and operations described herein. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher-level code that may be executed by a computing device such as a server or other data processing apparatus using an interpreter. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as flash memory, compact disk (CD) or digital versatile disk (DVD); magneto-optical media; and hardware devices specially configured to store program instructions, such as read-only memory (“ROM”) devices and random access memory (“RAM”) devices. A computer-readable medium may be any combination of such storage devices.

Any of the operations and techniques described in this application may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer-readable medium. Computer-readable media encoded with the software/program code may be packaged with a compatible device or provided separately from other devices (e.g., via Internet download). Any such computer-readable medium may reside on or within a single computing device or an entire computer system, and may be among other computer-readable media within a system or network. A computer system or computing device may include a monitor, printer, or other suitable display for providing any of the results mentioned herein to a user.

While various implementations have been described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present application should not be limited by any of the implementations described herein, but should be defined only in accordance with the following and later-submitted claims and their equivalents. 

What is claimed is:
 1. A system comprising: A database system for displaying a presentation of a dynamic page previewer for a server-hosted web application builder, the database system configurable to cause: maintaining a multi-tenant database associated with a plurality of users, the multi-tenant database identifying a plurality of web applications and web application components, the web application components configured to be reusable within the web application builder; causing, for display on a client device, a user interface for the dynamic page previewer, the user interface comprising a preview page of a web application from the plurality of web applications, the web application comprising one or more of the plurality of web application components and one or more component toggle buttons corresponding to the one or more web application components; processing a user request to select a component toggle button; determining one or more component visibility rules associated with the web application component corresponding to the selected component toggle button; determining a visibility state for the web application component; modifying the visibility state in relation to the one or more component visibility rules; and presenting, in response to the first user request and in the user interface, the preview page of the web application with the web application component being visible or not visible based on the modified visibility state.
 2. The system of claim 1, wherein the one or more component visibility rules comprise at least determining that one or more users have permission to access the web application component.
 3. The system of claim 1, wherein modifying the visibility state comprises setting the visibility state to not visible, and wherein presenting the web application comprises the web application not being visible.
 4. The system of claim 1, wherein the first user request comprises a user input within the user interface, the user input comprising at least one of a click, touch, or selection gesture directed at the component toggle button.
 5. The system of claim 1, wherein the one or more component visibility rules comprise at least one or more pieces of data from a user profile or user preferences section associated with a user.
 6. The system of claim 1, wherein the one or more component visibility rules comprise at least one or more values of one or more records being equal to or above one or more designated threshold values.
 7. The system of claim 1, wherein presenting the preview page in response to the first user request is performed in substantially real-time after processing the first user request.
 8. A method comprising: maintaining a multi-tenant database associated with a plurality of users, the multi-tenant database identifying a plurality of web applications and web application components, the web application components configured to be reusable within a web application builder; causing, for display on a client device, a user interface for the dynamic page previewer, the user interface comprising a preview page of a web application from the plurality of web applications, the web applications comprising one or more of the plurality of web application components and one or more component toggle buttons corresponding to the one or more web application components; processing a first user request to select a component toggle button; determining one or more component visibility rules associated with the web application component corresponding to the selected component toggle button; determining a visibility state for the web application component based on the one or more component visibility rules; modifying the visibility state in relation to the one or more component visibility rules; and presenting, in response to the first user request and in the user interface, the preview page of the web application with the web application component being visible or not visible based on the modified visibility state.
 9. The method of claim 8, wherein the one or more component visibility rules comprise at least determining that one or more users have permission to access the web application component.
 10. The method of claim 8, wherein modifying the visibility state comprises setting the visibility state to not visible, and wherein presenting the web application comprises the web application not being visible.
 11. The method of claim 8, wherein the first user request comprises a user input within the user interface, the user input comprising at least one of a click, touch, or selection gesture directed at the component toggle button.
 12. The method of claim 8, wherein the one or more component visibility rules comprise at least one or more pieces of data from a user profile or user preferences section associated with a user.
 13. The method of claim 8, wherein the one or more component visibility rules comprise at least one or more values of one or more records being equal to or above one or more designated threshold values.
 14. The method of claim 8, wherein presenting the preview page in response to the first user request is performed in substantially real-time after processing the first user request.
 15. A computer program product comprising computer-readable program code capable of being executed by one or more processors when retrieved from a non-transitory computer-readable medium, the program code comprising instructions configurable to cause: maintaining a multi-tenant database associated with a plurality of users, the multi-tenant database identifying a plurality of web applications and web application components, the web application components configured to be reusable within a web application builder; causing, for display on a client device, a user interface for the dynamic page previewer, the user interface comprising a preview page of a web application from the plurality of web applications, the web applications comprising one or more of the plurality of web application components and one or more component toggle buttons corresponding to the one or more web application components; processing a first user request to select a component toggle button; determining one or more component visibility rules associated with the web application component corresponding to the selected component toggle button; determining a visibility state for the web application component based on the one or more component visibility rules; modifying the visibility state in relation to the one or more component visibility rules; and presenting, in response to the first user request and in the user interface, the preview page of the web application with the web application component being visible or not visible based on the modified visibility state.
 16. The computer program product of claim 15, wherein the one or more component visibility rules comprise at least determining that one or more users have permission to access the web application component.
 17. The computer program product of claim 15, wherein modifying the visibility state comprises setting the visibility state to not visible, and wherein presenting the web application comprises the web application not being visible.
 18. The computer program product of claim 15, wherein the first user request comprises a user input within the user interface, the user input comprising at least one of a click, touch, or selection gesture directed at the component toggle button.
 19. The computer program product of claim 15, wherein the one or more component visibility rules comprise at least one or more pieces of data from a user profile or user preferences section associated with a user.
 20. The computer program product of claim 15, wherein the one or more component visibility rules comprise at least one or more values of one or more records being equal to or above one or more designated threshold values. 